docs: add ClickHouse analytics blog post - #686

…ents

Replace the cluster-migration walkthrough with the part readers actually care about: pointing a LibreChat agent at the ClickHouse data and asking it questions in plain English, the privacy stance behind it, and the ClickHouse partnership tie-in. The migration drops to a single line. Adds a prompts appendix and bumps Plausible to v3.2.1.

…gures

Adds two screenshots from the actual LibreChat agent session: the tool calls and data provenance, and the Key Insights answer. Corrects every number in the summary table against that run (Wednesday not Monday, 21% weekend share, Docker at 4.4x npm, and so on), and covers the engagement_time data-quality problem the agent flagged on its own.

Redates the post to its publication date so it matches the date range visible in the transcript, renaming the post and its images to suit.

The floppy-disk comparison was wrong: 28 MiB needs about twenty 1.44 MB disks, not half of one. Swapped it for a CD, which holds the dataset roughly twenty times over.

Blog posts are prerendered from generateStaticParams, and the SiteStats fallback performs no fetch, so a post embedding it was baked at build with no revalidation and a Plausible key added later could never take effect. Sets revalidate on the blog route so those pages regenerate hourly.

The shared blog rule pins every /blog document at s-maxage=86400, so the CDN could serve day-old numbers on a post that presents them as live, regardless of how often the origin regenerated. Adds a narrower rule for those paths at s-maxage=3600 to match the route's revalidate, keeping the RSC split so flight payloads stay uncacheable.